Internet Info 1994 March/Internet Info CD-ROM (Walnut Creek) (March 1994).iso/inet/netinfo/european-ip-template.txt

Text File | 1993-03-28 | 25KB | 1,036 lines

       EUROPEAN IP NETWORK NUMBER APPLICATION FORM &
                      SUPPORTING NOTES

                       23 March 1993

                  Document-ID: ripe-83.txt

                 Expiry Date: 30 June 1993






To whom it may concern.

Thank you for your request for an IP network number.  Please
ensure  that you read the information below carefully before
submitting your application for  an  IP  number.   The  form
appended  to  this letter will be accepted by local Internet
Registries (IR's) across Europe.

The  previously  centralised  procedures  for  obtaining  IP
network  numbers  from  the  Global  Internet  Registry (aka
[e-mail]) have been replaced by a  distributed
system  whereby  applications  for IP network numbers across
Europe are processed by Local Internet Registries.

The diagram below shows the distributed hierarchy  of  IR`s.
The  global  IR  delegates  blocks of IP numbers to the RIPE
NCC, who in turn delegates blocks of  IP  numbers  to  local
IR's.   Note  that  local  IR's are of two types, comprising
"service providers"  and  "non-service  providers".   An  IP
service  provider  is an organisation that supplies Internet
connectivity (examples are academic  network  providers  and
commercial network providers).  "Non-service provider" local
IR's are organisations  that  are  prepared  to  handle  all
requests  from  organisations that have no connection to the
Internet at  present  or  planned.   "Non-service  provider"
local IR's are organisations that are prepared to handle all
requests from organisations that have no connection  to  the
Internet at present or planned.












RIPE-83.TXT                                Expires 30-Jun-93
                           - 2 -



           Global IR  (DDN-NIC now known as Internic)
                           |
                           |
               Regional IR (RIPE NCC)
                           |
   ________________________|____________________
   |                 |             |           |
Local IR          Local IR      Local IR     Local IR
                                  /            /
 ( "NON SERVICE"    (SERVICE PROVIDERS)  (SERVICE PROVIDER)
       PROVIDER")


If you are NOT a customer of a service  provider,  then  you
should  send  your  completed  application  form to the "Non
Service Provider" local IR. Currently only one of this  type
of  registry  exists  per  country in Europe.  If you do not
know whether a local non-provider IR exists for your country
then you should contact the RIPE NCC (see address below). If
however, you are already a customer of an IP provider,  then
you should contact them for your IP network number.

Regardless of whether you are applying  for  class  B  or  C
addresses  you  should  always  make your application in the
first instance to a local IR.  However,  class  B  addresses
are only assigned by a Regional Internet Registry (in Europe
this is the RIPE NCC located in the Netherlands), so if your
application  is felt justified, it will be forwarded by your
local IR for the RIPE  NCC  to  review.   If  you  have  any
queries,  please do not hesitate to contact the RIPE NCC who
will be able to advise you. Our contact  details  are  given
below:


RIPE NCC                        email: [e-mail]
Kruislaan 409                   tel: [phone]
1098 SJ Amsterdam               fax: [phone]
The Netherlands


Yours sincerely.

[e-mail]

RIPE Network Coordination Centre











RIPE-83.TXT                                Expires 30-Jun-93
                           - 3 -


Supporting Notes for the IP Request Form

Before making your request for an IP  number,  there  are  3
documents which you should receive and read:


   THE EUROPEAN IP NUMBER REQUEST FORM:

   - appended to this document

   THE SUPPORTING NOTES:

   - this document

   THE HELPFUL HINTS DOCUMENT

   - this is document is currently being updated.

  (Until the new document is available, the old document
   "Helpful Hints for organisations requesting class B
    network numbers"  will be appended to this document).


This document will guide you in how to complete the European
IP  number request form correctly.  This form is used by all
the Internet Registries across Europe.  The  format  of  the
form  is  designed so that it enables your application to be
processed more quickly.  That is why we ask you to carefully
read  and  follow  the  "Supporting  Notes"  document  which
describes in detail how to complete the form.

Please be careful to follow the information contained within
the   examples  overleaf.   A  completed  template  is  also
included for reference. If you are unsure about any  of  the
fields,  please  leave them blank. Please send the completed
template to your local IR or contact the RIPE  NCC,  if  you
are unsure about what to do next.




















RIPE-83.TXT                                Expires 30-Jun-93
                           - 4 -


Part A - Administrative Details

The information supplied for this section together with  the
assigned  network numbers will be entered into a database of
European network numbers and their contact information which
is accessible by the whole Internet community.

NETWORK TEMPLATE


netname: Please complete with an  appropriate  network  name
         for  the  network to be numbered which is short and
         meaningful.   The  `netname'  is  used  mainly  for
         administrative  purposes  like consistency checking
         of the Internet Registry.  You will most likely not
         see  this  name  appear anywhere, but on forms like
         this.   The  network  name  should  be  written  in
         capital letters eg:

                 netname: TBIT


descr:   Please complete with a  short  description  of  the
         organisation,  including  the  location.   The full
         postal address is not needed as this is required in
         the person template eg:

                 descr:   Terabit Labs Inc.
                 descr:   Network Bugs Feeding Facility
                 descr:   Northtown


country: Please give the two letter country code (ISO  3166)
         which is appropriate for the organisation.  We know
         this gives problems for networks crossing  national
         boundaries, so choose the most appropriate country,
         based on the location of the admin contact.  If you
         do  not know the appropriate code for your country,
         please complete with the full name of  the  country
         eg:

                 country: NL


admin-c: Please complete with the name or NIC handle of  the
         person  who  is  the administrative contact for the
         network.  The NIC handle (if known)  is  preferred.
         Please do not use formal titles like `Dr' or `Prof'
         or `Sir'.  Please specify as in the  example  below
         (or  with  the  NIC  handle). Do not add full stops
         between the names or initials eg:






RIPE-83.TXT                                Expires 30-Jun-93
                           - 5 -



              admin-c: John E Doe  or
              use the NIC handle (if applicable)
              admin-c: JD58


tech-c:  Please give the name of  technical  contact  person
         (or  NIC  handle as mentioned above).  There can be
         more than one  name  specified  for  the  technical
         contact.   NOTE:  please  give  names  for both the
         administrative AND the technical contact.   If  two
         different  names are not appropriate, then the same
         name for both contacts is fine.  Example as above.

changed: Email address of the person who is  completing  the
         template,  followed by the current date.  If you do
         not have email connectivity please leave blank  and
         we  will  complete  it.  Please add the date in the
         format shown below eg:

              changed: [e-mail] 930225


source:  Source of the  information.   It   will  always  be
         RIPE.  This is information which is always required
         in the database, so it has been added already.

PERSON TEMPLATE

For each different person specified in the network template,
please  complete a separate person template, unless the data
about those persons is already in the RIPE database.

person: Please give the full name of the admin-c contact and
        the tech-c contact.  There must be a person template
        completed for each different  name  specified.   The
        names  must  be  written  identically to those given
        above in the  "admin-c:"  and  "tech-c:"  attributes
        above  (but  must not be the NIC handle) or official
        titles like "Dr, Prof or Sir"  eg:

             person: John E Doe


address:Please complete with the full  postal  address,  and
        write  as  you  would for ordinary postal mail using
        one line for each part of the address as shown below
        eg:

             address: Terabit Labs Inc.
             address: North Perpendicular Road 12
             address: NL-1234 Northtown
             address: The Netherlands




RIPE-83.TXT                                Expires 30-Jun-93
                           - 6 -


phone:  Please give the work telephone number of the  person
        specified above. Please specify the telephone number
        with + <country code> <area code> <telephone number>
        Most  countries  should  drop  the leading zero when
        specifying their area code.  More than one telephone
        number  is fine. Each telephone number should be put
        on a separate line and written in order of the  most
        appropriate number for the contact person eg:

             phone: [phone]
             phone: [phone] ext.  4711


fax-no: Please complete  with  the  telefax  number  of  the
        person  specified  above. Follow with the same rules
        as specified for telephone number above eg:

             fax-no: [phone]


e-mail: Please  supply  the  appropriate   electronic   mail
        address  for  the contact. If you DO NOT have e-mail
        connectivity, please insert <none>.   Please  ensure
        that this is a valid domain address eg:

             e-mail: [e-mail] or
             e-mail: <none>


nic-hdl:This refers to  a  NIC  handle  which  is  a  unique
        identifier  assigned  and  used  by  the  US  NIC to
        unambiguously refer to Internet people.  If  you  do
        not have a NIC handle, then please leave blank eg:

             nic-hdl: JD0401


changed:Who and when changed  this  last.   Please  complete
        with  your  e-mail  address  followed by the current
        date in the format which is shown below.  If you  do
        not have e-mail connectivity, please leave blank and
        we will complete this on your behalf eg:

             changed: [e-mail] 930225


source: Source of the information.  This will always be RIPE
        and is a required field so it has been added









RIPE-83.TXT                                Expires 30-Jun-93
                           - 7 -


Part B - Technical Details

Information supplied below helps us to evaluate and  process
your  request.It  will  be  kept  IN  CONFIDENCE  by  us for
internal use only.  It will NOT be  entered  into  the  RIPE
Network Management Database.

TECHNICAL TEMPLATE


request-type:
        Please  specify  the  quantity  and  class  of  your
        request for network numbers.

        In making the application, please be guided  by  the
        following  EXAMPLES  of number of hosts which relate
        to the quantity of network numbers requested eg:

           1 class C number     (maximum 254 hosts)
           2 class C numbers    (maximum 508 hosts)
           4 class C numbers    (maximum 1016 hosts)
           8 class C numbers    (maximum 2032 hosts)
           16 class C numbers   (maximum 4064 hosts)
           32 class C numbers   (maximum 8128 hosts)
           a single class B number
           other (please specify)


machine-0:
        Please  state  the  number  of  machines   in   your
        organisation  that  currently  require  a  unique IP
        address.  Do not forget to include terminal  servers
        and network numbers needed for transit networks when
        calculating this figure eg:

            machine-0: 100


machine-1:

machine-2:
        As above for machine-0 but  estimate  for  1  and  2
        years time.

subnet-0:Please state the number of subnets required for the
        current  network.   A  subnet refers to the physical
        parts of the network which need  a  unique  (sub)net
        number eg:

             subnet-0: 10


subnet-1:




RIPE-83.TXT                                Expires 30-Jun-93
                           - 8 -


subnet-2:As above for subnet-0 but estimate for  the  number
        of subnets in 1 and 2 years time.

inet-connect:
        Please state whether you  plan  to  connect  to  the
        Internet.   Please  answer  with  whichever  of  the
        following  options  most   closely   describes   the
        position of your organisation eg:

             - will never connect
             - already connected <through whom>
             - plan to connect <date> <through whom>

        If you are  "already  connected"  to  the  Internet,
        please   state   which   service  provider  you  are
        connected to.  If you answer with "plan to  connect"
        then  please make an estimation on the date that you
        hope to connect, specifying the month, the year  (if
        possible) and through whom if known eg:

             inet-connect: plan to connect 930401 Net-Provider Inc


exist-IP-net:
        Has your organisation already obtained an IP network
        number  or  numbers?  If so, please give the network
        number(s) and the network name  if  known.  If  not,
        then please complete with <no>.Format: complete with
        the network number only - four numbers separated  by
        dots, as shown below.  If known, please also add the
        network name entry as shown  below.   This  must  be
        specified  in  exactly  the  same  way as it appears
        below eg:

             exist-ip-NET: 193.87.45.0 TBIT or
             exist-IP-net: <none>


net-country:
        Please  give  the  ISO  3166  country   code   which
        describes  where  the  network  will be located.  If
        more than one country applies, then give  the  names
        of  the  countries   which  will  be  covered by the
        network. Format: complete with the  country  name(s)
        using  the ISO 3166 country code.  If you are unsure
        about the code, write the name  of  the  country  in
        full.

             net-country: NL SE








RIPE-83.TXT                                Expires 30-Jun-93
                           - 9 -


EXAMPLE COMPLETED NETWORK, PERSON and TECHNICAL TEMPLATE

netname: TBIT
descr:   Terabit Labs Inc.
descr:   Network Bugs Feeding Facility
descr:   Northtown
country: NL
admin-c: John E Doe
tech-c:  John E Doe
changed: [e-mail] 930225
source:  RIPE

person:  John E Doe
address: Terabit Labs Inc.
address: Industrial Estate North
address: North Perpendicular Road 12
address: NL-1234 Northtown
address: The Netherlands
phone:   [phone] ext.  4711
fax-no:  [phone]
e-mail:  [e-mail]
nic-hdl: JD0401
changed: [e-mail] 930225
source:  RIPE

request-type: 1 class C
machine-0:    100
machine-1:    134
machine-2:    250
subnet-0:     1
subnet-1:     1
subnet-2:     1
inet-connect: plan to connect 930401 Net-Provider Inc
exist-IP-net: 193.87.45.0 TBIT
net-country: NL






















RIPE-83.TXT                                Expires 30-Jun-93
                           - 10 -


Part C - Technical Details

Please complete this section on a separate page if  you  are
applying  for more than 2 Class C network numbers.  The more
numbers you are requesting, the more detailed your technical
description  will  need to be.  Furthermore, the more detail
you provide, the quicker we will be  able  to  process  your
application.  Please include an overview of the size of your
subnets, ensuring that you do not forget  transit  networks,
terminal servers etc.  when calculating your needs.

Before  you  complete  this  section  you  should  read  the
`Helpful  Hints'  document  (currently  being updated) which
will guide you.  It is particularly important to  read  this
document  if  you are applying for a class B network number,
as it provides additional hints.  Until  this  document  has
been updated, the "Additional Hints" will be appended.

If you are applying for a Class B network number please send
your  completed  application  to the local registry who will
review your case. If it is  felt  that  a  Class  B  network
number  is  justified, your application will be forwarded to
the RIPE NCC who will review your  application.   Please  be
reminded  that  Class B network numbers are extremely scarce
and are rarely allocated.

Part D - Contact Details

This section should be completed *ONLY IF* you are making an
application  on  behalf  of  another  organisation.   Please
indicate who the application is being made by and on  behalf
of whom, giving all the contact details requested.

























RIPE-83.TXT                                Expires 30-Jun-93
                           - 11 -


Recommended Reading List for Address Allocation and CIDR


1. rfc1338.txt - Supernetting: an Address Assignment and
   Aggregation Strategy (V Fuller)
2. rfc 1366.txt - Guidelines for Management of IP Address
   Space (E Gerich)
3. rfc1367.txt  - Schedule for IP Address Space Management
   Guidelines (C Topolcic)


The documents you require are all contained within the  RIPE
document  store  in  the  rfc/ directory.  The RIPE document
store can be accessed in a number of ways:


1. on the Internet type: telnet info.ripe.net
2. on the Internet via anonymous FTP from host ftp.ripe.net
3. using the IXI network type: pad 020430459300031
4. via the Public Data Network type: pad 0204129004331


Additional  Hints  for  Organisations  Requesting  Class   B
Network Numbers

Please understand that the criteria for allocating  Class  B
network  addresses are extremely strict.  This is due to the
global scarcity of these network numbers.  Out of  necessity
then, your local registry and the NCC has to closely examine
each and every  request  received  for  a  class  B  network
address.   As  a  result  the  allocation  process will take
longer.  Organisations can however speed up the  process  by
providing  as  much information as possible on their initial
request to enable a decision to be made  without  having  to
request more information.

The number of hosts estimates should be  substantiated  with
other data about the network and/or organisation like number
of employees, geographical distribution, type of hosts.  The
clearer  you  can document that your estimates are carefully
derived, the easier it is for us to justify allocation of  a
class B address.

Besides a sufficient number of hosts we must determine  that
your   network  cannot  be  engineered  using  a  number  of
contiguous class C networks.  If your network consists of  a
large  number  of  physical  networks  with relatively small
numbers  of  hosts  on  each,  you  will  have  to  consider
subnetting  class C networks.  A large number of subnetworks
alone is not sufficient justification for  allocation  of  a
class  B  network  number.   We  realise  that  a  number of
engineering  decisions  can  be  based   on   administrative
convenience.   Unfortunately  the  remaining class B address
space  is  too  small  to  take  these  considerations  into



RIPE-83.TXT                                Expires 30-Jun-93
                           - 12 -


account.   The  clearer  your explanation is, as to why your
network *cannot* be engineered using  a  block  of  class  C
network  numbers,  the  easier  it  is  for  us  to  justify
allocation of a class B network address.

Besides a sufficient number of hosts we must determine  that
your   network  cannot  be  engineered  using  a  number  of
contiguous class C networks.  If your network consists of  a
large  number  of  physical  networks  with relatively small
numbers  of  hosts  on  each,  you  will  have  to  consider
subnetting  class C networks.  A large number of subnetworks
alone is not sufficient justification for  allocation  of  a
class  B  network  number.   We  realise  that  a  number of
engineering  decisions  can  be  based   on   administrative
convenience.   Unfortunately  the  remaining class B address
space  is  too  small  to  take  these  considerations  into
account.   The  clearer  your explanation is, as to why your
network *cannot* be engineered using  a  block  of  class  C
network  numbers,  the  easier  it  is  for  us  to  justify
allocation of a class B network address.

All the above mentioned points apply even more  strongly  to
cases  where multiple class B network numbers are requested.
Assignments of multiple class B network  numbers  will  only
occur  when  your  local  registry  and  the  RIPE  NCC  are
satisfied with a detailed  justification  in  terms  of  the
criteria mentioned.

Finally, please understand that we are not  working  against
you, but with the whole Internet community to achieve a fair
distribution of the remaining address space.   If  you  have
any questions about the procedure or the information needed,
please do not hesitate to contact the your local registry or
the RIPE NCC for further guidance.























RIPE-83.TXT                                Expires 30-Jun-93
                           - 13 -


COMPLETE FORM BELOW AND DETACH HERE 8< -----

EUROPEAN INTERNET NUMBER REQUEST FORM

Email is preferred if you have  it.   If  not,  then  it  is
preferred  if  you  send in your template by fax.  This will
help us to process your request more quickly.

Once completed, please return this document to your local IR
or  to the RIPE NCC if this is appropriate or you are unsure
(the address for the RIPE NCC is given on page 1).

IMPORTANT NOTE

This document is valid until June 30th,  1993.   An  updated
document will be sent out when due.

Part A - Administrative Details

The information supplied for this section together with  the
assigned  network numbers will be entered into a database of
European network numbers and their contact information which
is accessible by the whole Internet community.

NETWORK TEMPLATE


inetnum:
number:
netname:
descr:
descr:
country:
admin-c:
tech-c:
connect:
changed:
source: RIPE


PERSON TEMPLATE

person:
address:
address:
address:
address:
phone:
fax-no:
e-mail:
nic-hdl:
changed:
source: RIPE




RIPE-83.TXT                                Expires 30-Jun-93
                           - 14 -



PERSON TEMPLATE

person:
address:
address:
address:
address:
phone:
fax-no:
e-mail:
nic-hdl:
changed:
source: RIPE


Please note that you will have to include a separate  person
template  for each person referenced as a contact unless the
information about the person in the RIPE database  is  still
valid.

The information given above will be entered into a  database
of  European  network  contacts  which  is accessible by the
whole Internet community.  Please  refer  to  the  RIPE  NCC
leaflet  on the "Network Management Database" for details on
how to query the database.































RIPE-83.TXT                                Expires 30-Jun-93
                           - 15 -


Part B - Technical Details

Information supplied below helps us to evaluate and  process
your  request.   It will be kept in strict CONFIDENCE and is
for internal use only.  It will NOT be entered into the RIPE
Network Management Database.

TECHNICAL TEMPLATE


request-type:
machine-0:
machine-1:
machine-2:
subnet--0:
subnet-1:
subnet-2:
inet-connect:
exist-IP-net:
net-country:

Part C - Technical Details

If you are applying for more than 2 Class C network  numbers
then  on  this  page,  please  submit  a description of your
network plans.   Please  continue  on  a  separate  page  if
necessary.

Current network layout   :








Future network plans    : (next 2 years)



















RIPE-83.TXT                                Expires 30-Jun-93
                           - 16 -


Part D - Contact Details

Complete the section below  *ONLY  IF*  you  are  making  an
application on behalf of another organisation.

This application is made by:-

name:
organisation:
country:
phone:
fax-no:
e-mail:

On behalf of the following organisation:

name:
organisation:
country:
phone:
fax-no:
e-mail:



































RIPE-83.TXT                                Expires 30-Jun-93
                           - 17 -



























































RIPE-83.TXT                                Expires 30-Jun-93